lsvpd for Linux.

Introduction
------------

The Linux(R) lsvpd package is a partial reimplementation, for Linux,
of some AIX(R) hardware inventory and configuration commands.  The
focus is on providing the same level of serviceability on IBM(R)
pSeries(R) hardware as is provided by AIX.  The main function is to
list Vital Product Data (VPD) about hardware components, including
systems, adapters and devices, in a variety of ways.

Documentation
-------------

* For usage information, see lsvpd(8), lscfg(8), lsmcode(8), lsvio(8),
  update-lsvpd-db(8).

* Extra documentation:

  - Installation notes, see install.{xml,html}.

  - Design/implementation notes, see design.{xml,html}.

  These will either be installed with your package or are in the docs/
  subdirectory of the source distribution.

Bugs?
-----

If things aren't working as you'd expect please send a bug report.
Useful (and often necessary) information to include in your bug report
includes:

* Output, along with a comment about what is wrong with it!

* Version of lsvpd.

* Installation method?  From source, from a package... where did you
  get the package?

* Kernel version.  Probably the output of "uname -a".

* Information about the type of machine.  Sometimes this just lets me
  know if it is a type of machine that I've already tested on.

* Output of "mount".

Most of the above (and more) can be accomplished by using the script
/lib/lsvpd/lsvpd_test.  By default this script will produce several
files in the current directory, including:

    lsvpd-scan.trace-VERSION:
	Output of "bash -x /sbin/update-lsvpd-db -d >lsvpd-scan.trace 2>&1".
    linux.lsvpd-VERSION:
	Output of "lsvpd".
    linux.lscfg-vp-VERSION:
	Output of "lscfg -vp".
    linux.lsmcode-A-VERSION:
	Output of "lsmcode -A"
    linux.lsvio-sed-VERSION:
	Output of "lsvio -sed"

On complex systems, the trace can be very big.  Note that the trace
will contain a lot of information about your system, but shouldn't
include anything sensitive (unless, of course, you have sensitive
pre-release hardware!).  Use your discretion when deciding whether you
should send it to the maintainers.

Sending the maintainers a trace like the above is very helpful for
debugging a variety of problems, including spurious warning/error
messages from update-lsvpd-db and missing information for certain
(types of) adapters/devices.

To email these files to someone automatically, use:

# /lib/lsvpd/lsvpd_test -m <EMAIL-ADDRESS>

This will also send an archive of the current database (whatever
/var/lib/lsvpd/db points to).

Note that this script has no facility to send comments, so you'll need
to send a separate email containing any comments.

Maintainers
-----------

Maintained by:

* Brad Peters <bpeters@us.ibm.com>,
* Eric Munson <munsone@us.ibm.com>

Previously maintained by:

* Martin Schwenke <martins@au.ibm.com>
* Keith Matthews  <keith@au.ibm.com>
